Systems and methods for embedding metadata into video contents

ABSTRACT

There is provided systems and methods for embedding data into a video content. A system includes an encoder, a memory storing the encoder, and a hardware processor configured to execute the encoder from the memory. The hardware processor is configured to execute the encoder from the memory to obtain the data, determine a plurality of pixels in the video content, and embed the data into the video content by inverting the plurality of pixels in the video content according to the data. The system further includes a decoder for decoding the video content to obtain the data.

BACKGROUND

Conventionally, when a video content is being streamed to a device, thedevice needs information in addition to the video content foridentifying the video content. For example, conventionally, the devicerelies on metadata accompanying and separate from the video content toidentify the video content. However, the metadata may not be reliableinformation due to alterations during format conversion, error duringcreation of the metadata, lack of metadata, or unintelligible metadataformat. Even more, especially with recorded or duplicated video content,the metadata associated with the video content is stripped and notaccompany the video content being streamed to the device. As a result,the device cannot make the viewer aware of the identity of the videocontent, and the device will be incapable of labeling, indexing, andmanaging the video content effectively.

SUMMARY

The present disclosure is directed to systems and methods for embeddingmetadata into video contents, substantially as shown in and/or describedin connection with at least one of the figures, as set forth morecompletely in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 presents a system for embedding metadata into video contents,according to one implementation of the present disclosure.

FIG. 2A presents an example of an encoded frame of a video content,according to one implementation of the present disclosure.

FIG. 2B presents an example of a decoded frame of a video content,according to one implementation of the present disclosure.

FIG. 3A presents another example of an encoded frame of a video content,according to one implementation of the present disclosure.

FIG. 3B presents another example of a decoded frame of a video content,according to one implementation of the present disclosure.

FIG. 4 shows a flowchart illustrating a method for embedding metadatainto video contents, according to one implementation of the presentdisclosure.

FIG. 5 shows a flowchart illustrating a method for retrieving metadatafrom video contents, according to one implementation of the presentdisclosure.

DETAILED DESCRIPTION

The following description contains specific information pertaining toimplementations in the present disclosure. The drawings in the presentapplication and their accompanying detailed description are directed tomerely exemplary implementations. Unless noted otherwise, like orcorresponding elements among the figures may be indicated by like orcorresponding reference numerals. Moreover, the drawings andillustrations in the present application are generally not to scale, andare not intended to correspond to actual relative dimensions.

FIG. 1 presents a system for embedding metadata into video contents,according to one implementation of the present disclosure. System 100 ofFIG. 1 includes server 110, network 130, client device 150, display 170,and input device 172. Server 110 includes server processor 112,communication interface 114, and memory 122. Memory 122 includes encoder126, video content 123, and metadata 125. Encoder 126 is an algorithmfor execution by server processor 112 to encode metadata 125 into videocontent 123 according to encoder settings 127 for generating videocontent with encoded metadata 128. Client device 150 includes processor152, input interface 154, communication interface 156, and memory 158.Memory 158 includes decoder 160, which is an algorithm for execution byprocessor 152 to decode video content with encoded metadata 128 usingdecoder settings 129 to obtain metadata 125.

Server 110 is configured to communicate with client device 150 acrossnetwork 130 to provide video content with encoded metadata 128 to clientdevice 150. Server 110 may be configured to stream video content withencoded metadata 128 to client device 150 over network 130, such as theInternet, or in some implementations, server 110 may be configured totransmit all, or part, of video content with encoded metadata 128 toclient device 150 for storage on memory 158 of client device 150. Forexample, server 110 may be operated by a content provider. In someimplementations, server 110 may be a local server, where network 130 isa local area network (LAN) and video content with encoded metadata 128may be streamed or played locally across network 130.

Also illustrated in FIG. 1, server 110 includes server processor 112 andmemory 122. Server processor 112 may be configured to access memory 122to store received input or to execute commands, processes, or programsstored in memory 122. Server processor 112 may correspond to aprocessing device, such as a microprocessor or similar hardwareprocessing device, or a plurality of hardware devices. Memory 122 iscapable of storing commands, processes, and programs, such as encoder126, for execution by server processor 112. Memory 122 may be institutedas ROM, RAM, flash memory, or any sufficient memory capable of storing aset of commands and data, such as encoder settings 127 and metadata 125.In other implementations, memory 122 may correspond to a pluralitymemory types or modules.

Also shown in FIG. 1, server 110 also includes communication interface114. Server 110 may utilize communication interface 114 to communicatewith communication interface 156 of client device 150 over network 130.Communication interface 114 can utilize, as examples, one or more ofEthernet, Wireless Fidelity (Wi-Fi), Worldwide Interoperability forMicrowave Access (WiMax), ZigBee, Bluetooth, RFID, Algorithm DivisionMultiple Access (CDMA), Evolution-Data Optimized (EV-DO), Global Systemfor Mobile Communications (GSM), Long Term Evolution (LTE), and othertypes of wired and wireless interfaces.

Memory 122 includes video content 123. Video content 123 includes videoand may also include audio, text, still frame, photographic, and/orother types of content that include pixels. For example, content 124 maybe a television show, a movie, a live broadcast, a photo album, anindividual photo, or another type of visual content. Content 124 is thecontent in its original form, prior to being encoded by encoder 126.Content 124 may take a wide variety of formats, such as, for example,Flash, MPEG-1, MPEG-2, QuickTime, Windows Media Video, RealMedia, orWebM. It should be noted that in some implementations, video content 123may be replaced with any type of content that includes pixels, such asany still images or photographs. Therefore, the present application isnot limited to video contents and is also applicable to still images,and metadata 125 may describe the still image.

as shown in FIG. 1, memory 122 also includes metadata 125, which may bedata that describes the video content or is associated with videocontent 123. For example, metadata 125 may include a title, a genre, acast list, a tribune (TMS) ID, an air date, a capture date, an episodename, an episode number, and/or other data associated with video content123. In another example, metadata 125 may include authenticity dataconfigured for output to a viewer to inform the viewer that videocontent 123 is valid and/or legal.

Metadata 125 may also be personalized data generated by a user forpresenting with video content 123. In such an example, metadata 125 mayinclude a greeting for a user of client device 150, or anotherpersonalized communication. As such, metadata 125 can be any datacapable of being embedded into video content 123 using encoder 126.

In some implementations, metadata 125 may include advertisinginformation that can be dynamically embedded into video content 123using encoder 126 for streaming of video content with encoded metadata128 to client device 150. In such an implementation, metadata 125 mayinclude a uniform resource locator (URL), an image, and/or otheradvertising data that can be embedded into video content 123. As such,once video content with encoded metadata 128 is transmitted to clientdevice 150, client device 150 can dynamically display the advertisingcontent to the user of client device 150 through display 170.

Encoder 126 is configured to encode metadata 125 into video content 123to create video content with encoded metadata 128. Encoder 126 may beconfigured to embed or encode all of metadata 125 into video content124, or only certain data of metadata 125. Encoder 126 is configured todetermine how much of metadata 125 is to be embedded or encoded intovideo content 123, and then determine how many frames of video content123 are required to embed metadata 125 into video content 123.

In one implementation, encoder 126 encodes or embeds metadata 125 intovideo content 123 by inverting pixels in a selected region of a frame ofvideo content 123. For example, metadata 125 is coded with a binaryrepresentation of 0's and 1's by inverting pixels in a selected regionof a frame of video content 123. In some implementations, depending onencoder settings 127, inverted pixels are represented with 0's, andnon-inverted pixels are represented with 1's. However, in otherimplementations, depending on encoder settings 127, the non-invertedpixels may be represented with 0's, and the inverted pixels in may berepresented with 1's. As such, metadata 125 is embedded or encoded intoa selected region of a selected frame of video content 123.

In one implementation, encoder 126 selects a region in a frame of videocontent 123, such that the selected region has pixels with substantiallysimilar color, e.g. a dark color, or a light color, such as black orwhite, respectively. In an example implementation, the selected regionmay be defined by a matrix of pixels, e.g., 10×10, 20×20, 10×20, etc.Pixels within the selected region are then altered to insert metadata125 into the selected region of video content 213.

In one implementation, encoder 126 may also determine that the length ofmetadata 125, which is to be embedded into content 123 requires to beembedded in a plurality of frames of video content 123. As such, encoder126 may scan each frame of video content 124 to determine which framesof video content 124 are suited for embedding metadata 125. In order tomake the determination, in one implementation, encoder 126 may scan theframes of video content 123 for regions within each frame that includepixels of substantially identical color.

In one implementation, encoder 126 may embed metadata 125 into videocontent 124 using identical sized matrices of pixels, and/or may usedifferent sized matrices of pixels for each frame. For example, encoder126 may embed metadata 125 using 10×10, 20×20, 30×30, 200×200, 10×20,20×30, or other any sized matrices. Encoder 126 may be configured toutilize the size of the matrices to aid in making the above describeddetermination of which frames of video content 123 are suited forembedding metadata 125. For example, if encoder 126 determines that amatrix of metadata 125 is to be 10×10 pixels, encoder 126 may search forframes with regions that include at least a 10×10 matrix of pixels ofsubstantially the same color to ensure that the 10×10 matrix of embeddedmetadata 118 a fits within the region.

Once the frame or frames of video content 123 are determined by encoder126, encoder 126 is configured to embed metadata 125 into video content123. In order to embed metadata 125 into content 123, encoder 126 isconfigured to invert the pixels of the selected matrix or matricesaccording to metadata 125.

In some implementations, the matrices of the embedded metadata 125 arein the same location of each selected frame. For example, a 10×10 matrixmay be embedded at a certain position within a first frame, and the same10×10 matrix location may be selected for one or more other frames thatare encoded using embedded metadata 125. However, in otherimplementations, the matrices of embedded metadata 118 b may be indifferent locations in each frame. For example, a first 10×10 matrix maybe embedded in a top right corner region of a first frame, and a second10×10 matrix may be embedded in the bottom left corner region of asecond frame.

In some implementations, the matrices may be fenced, meaning that eachof the corners of the matrices may include a “1” where the “1” isembedded as an inverted or a non-inverted pixel depending on encodersettings 127. For example, if metadata 125 is embedded using a 10×10matrix, then a “1” may be embedded at positions (from top left to bottomright) 0:0, 10:0, 0:10, and 10:10 in order to form a fence at the fourcorners of the matrix. Such an implementation enables decoder 160 and/orclient device 150 to recognize embedded metadata 125 within videocontent with encoded metadata 128.

Encoder settings 127 may include the allowable sizes of matrices forembedding metadata 125, the allowable number of frames in video content123 for encoding metadata 125, the binary code distinctions for theinverted and non-inverted pixels, instructions for determining one ormore regions within frames of content 123 that include pixels ofsubstantially similar color, and the color of regions that may beselected. Encoder settings 127 may differ for different video contentsdepending on the format of video content 123. In some implementations,server 110 may also communicate encoder settings 127 to client device150 for use as part of decoder settings 129. In such an implementation,decoder 160 is configured to utilize encoder settings 128 as part ofdecoder settings 129 in order to more efficiently decode video contentwith encoded metadata 128.

In one implementation, in order to determine which regions within eachframe include pixels of substantially identical color, encoder settings127 may include at least one of a bias and a threshold. The bias defineshow similar in color pixels to the left and right of an examined pixelmay be in order to be considered as a region including pixels ofsubstantially identical color. The threshold defines which pixels, wheninverted, would yield meaningful or non-meaningful data, such as regionsincluding medium colored pixels. As such, the threshold providesinstructions as to how light or how dark the color of a region must bein order to be considered as a region including pixels of substantiallyidentical color.

Turning to client device 150 of system 100, client device 150 includesprocessor 152 and memory 158. Processor 152 may be configured to accessmemory 158 to execute decoder 160, store received input or to executecommands, processes, or programs stored in memory 158. Processor 152 maycorrespond to a processing device, such as a microprocessor or similarhardware processing device, or a plurality of hardware devices. Memory158 is capable of storing commands, processes, and programs forexecution by processor 152. Memory 158 may be instituted as ROM, RAM,flash memory, or any sufficient memory capable of storing a set ofcommands. In other implementations, memory 158 may correspond to aplurality memory types or modules. Client device 150 may be a cellularphone, a computer, a tablet computer, an optical player, or any devicecapable of playing back a video content.

Also illustrated in FIG. 1, client device 150 includes communicationinterface 156. Client device 150 may utilize communication interface 156to communicate with communication interface 114 of server 110 overnetwork 130. Communication interface 156 can utilize, as examples, oneor more of Ethernet, Wireless Fidelity (Wi-Fi), WorldwideInteroperability for Microwave Access (WiMax), ZigBee, Bluetooth, RFID,Algorithm Division Multiple Access (CDMA), Evolution-Data Optimized(EV-DO), Global System for Mobile Communications (GSM), Long TermEvolution (LTE), and other types of wired and wireless interfaces.

Input interface 154 of client device 150 is configured to communicatewith input device 172 and display 170. Input interface 154 maycommunicate with input device 172 and display 170 by a wired and/or awireless connection. Processor 152 of client device 150 is configured tocontrol input interface 154 to communicate with input device 172 anddisplay 170. Input interface 154 can utilize, for example, Wi-Fi, WiMax,ZigBee, Bluetooth, Bluetooth low energy, GSM, LTE, and other types ofwired and wireless technologies to communicate with input device 172 anddisplay 170.

Input device 172 of system 100 may include any devices necessary forinteracting with client device 150 and/or display 170. For example,input device 172 may include a keyboard, a microphone, a mouse, aheadset, a display, a remote, or any other device. In the presentimplementation, input device 172 is connected externally to clientdevice 150. However, in some implementations, input device 172 may bebuilt into client device 150, such as if client device 150 is a cellularphone, for example.

Display 170 is configured to display a video content or an image.Display 170 may communicate with client device 150 through inputinterface 154. Display 170 may comprise a liquid crystal display(“LCD”), a light-emitting diode (“LED”), an organic light-emitting diode(“OLED”), or another suitable display screen that performs a physicaltransformation of signals to light. In the present implementation,display 170 is connected externally to client device 150. However, inother implementations, display 160 may be built into client device 150and be configured for touch recognition. In such an implementation,display 170 is at least one of the devices making up input device 172.

Once client device 150 receives video content with encoded metadata 128using communication interface 156 from server 110 via network 130,processor 152 stores video content with encoded metadata 128 in memory158. Client device 150 is configured to determine the selected region orregions of one or more frames of video content with encoded metadata 128that have been encoded using metadata 125, and decoded the selectedregion or regions to obtain metadata 125. In some implementations,client device 150 may playback video content with encoded metadata 128without re-inverting the altered pixels to place them in the originalstate, i.e. the state before encoding by encoder 126 of server 110. Insuch an implementation, the frames including the embedded metadata 118 cincluding inverted pixels are displayed during playback. Because theamount of inverted pixels may be minimal and may be in one or a fewframes, viewers may not notice the inverted pixels. Also, because theinverted pixels may be included in regions of substantially similarlycolored pixels and non-focal point regions of the frames, viewers maynot notice the inverted pixels. In other implementations, however,decoder 160 may re-invert the altered pixels of video content withencoded metadata 128 to create video content 123, i.e. the originalvideo content, and client device 150 plays back video content 123.

In some implementations, metadata 125 may only be embedded into tenframes of thousands of frames. In such an example, the embedded metadata125 may only constitute a 10×10 matrix of pixels in each of the tenframes, where only a portion of the pixels in the 10×10 matrix areinverted, according to metadata 125. Further, each 10×10 matrix may bein a substantially black region of each of the ten frames, where thesubstantially black region is in the bottom right corner of each of theten frames (e.g., FIG. 3A for further illustration.) As such, in such anexample, during playback of video content with encoded metadata 128, theuser may never recognize alterations to the 10×10 matrices within theten frames of encoded content 116 b.

As discussed above, decoder 160 is configured to decode video contentwith encoded metadata 128 to obtain metadata 118 d and may create videocontent 123. Decoder 160 is further configured to determine how manyframes and which frames of video content with encoded metadata 128include metadata 125.

In some implementations, in order to determine which frames of videocontent with encoded metadata 128 include metadata 125, decoder 160utilizes an algorithm to search for inverted pixels within frames ofvideo content with encoded metadata 128, detect regions that includemetadata 125, obtain metadata 125, and then invert the inverted pixelsback to their original state to create video content 123. Decoder 160may use an algorithm similar to a Bayer Interpolation, similar to thatof cameras.

In one implementation, the decoder algorithm examines each pixel bycomparing such pixel to the pixel to the left and the pixel to theright. The decoder algorithm then inverts the pixels to the left and tothe right of the examined pixel and if the resulting color is similar tothe examined pixel, the algorithm may assume that the examined pixel iscoded for metadata 125, and that the examined pixel is part of a codedmatrix. In some implementations, the decoder algorithm may examine aregion of pixels and detect wide variances between the examined pixeland all of those around the examined pixel, and once a determination ismade that the examined pixel is different than the surrounding pixels,the examined pixel is determined to be a part of coded metadata 125.

In some implementations, decoder 160 may be aware of the location ofencoded regions based on encoder settings 128 transmitted to clientdevice 150 by server 110. In such an implementation, decoder 160 mayknow the frames of encoded content 116 b that include metadata 125, andalso the location of metadata 125 within those frames. As such, decoder160 is configured to obtain metadata 125 for output and utilization byclient device 150, and also to decode encoded content 116 b to invertthe inverted pixels within the frames of video content with encodedmetadata 128 to create video content 123.

Once the decoder algorithm has determined the location of the embeddedmetadata 125 within video content with encoded metadata 128, decoder 160is configured to obtain metadata 125 for use and output by client device150. For example, decoder 160 determines the proper binary code, 1's and0's, included within frames of video content with encoded metadata 128to obtain metadata 125.

In some implementations, for example, client device 150 may utilizemetadata 125 to organize, manage, and/or sort through content on clientdevice 150, including video content 123. In another example, clientdevice 150 may utilize metadata 125 to output information relating tovideo content 123 on display 170 for viewing by the user. In yet anotherexample, client device 150 may utilize metadata 125 to output personalmessages included in metadata 125, or to output authenticity informationto display 170 to authenticate video content 123 as being a legal and/orvalid copy of video content 123. In one example implementation, metadata125 may not described video content 123, but metadata may be dataassociated with video content 123 for authentication purposes. In suchan example, metadata 125 may be used to alter pixels in a frame of videocontent 123 to create a picture abnormality. In such an implementation,server 110 can communicate to client device 150 that at least one frameincludes at least one picture abnormality and communicate the locationof the at least one picture abnormality to client device 150. Clientdevice 150 may detect and verify the picture abnormality as part of anauthentication process to ensure that video content 123 is an authenticcopy.

Referring now to FIG. 2A, FIG. 2A presents an example of an encodedframe of a video content, according to one implementation of the presentdisclosure. Display 270 a of FIG. 2A includes encoded frame 217. Encodedframe 217 includes object 274 a, object 274 b, and object 274 c. Object274 a includes inverted pixel region 280 a. It should be noted thatdisplay 270 a corresponds to display 170 of FIG. 1.

Illustrated in FIG. 2A, display 270 a includes encoded frame 217.Encoded frame 217 may be one of frames embedded with metadata asdiscussed in FIG. 1 above. When determining where to embed the metadata,the encoder determines where a region of substantially consistent colorexists in encoded frame 217, such as encoder 126 of FIG. 1. In encodedframe 217, each of object 274 a, objects 274 b, and object 274 c includea shadow portion of consistent gray color. As such, the encoder mayrecognize any of the regions as a region to embed the metadata. Objects274 a includes the consistently gray color region in the bottom rightcorner of encoded frame 217, which may be another beneficial region toembed metadata so a viewer will not notice the inverted pixels duringplayback of the encoded content that includes encoded frame 217.

Also illustrated in FIG. 2A, encoded object 274 a of encoded frame 217includes inverted pixel region 280 a. Inverted pixel region includeswithin it a 4×4 matrix, where some of the gray pixels are inverted(inverted pixels are shown in white). In some implementations, graypixels may denote 1's and white pixels may denote 0's for embeddingmetadata into encoded frame 217. However, in other implementations, graypixels may denote 0's and white pixels may denote 1's. As such, when adecoder decodes encoded frame 217, the embedded metadata can be obtainedfrom the pixels in the 4×4 grid of encoded frame 217.

Referring now to FIG. 2B, FIG. 2B presents an example of a decoded frameof a video content, according to one implementation of the presentdisclosure. Display 270 b of FIG. 2B includes decoded frame 219. Decodedframe 219 includes object 274 a, object 274 b, and object 274 c. Object274 a includes inverted pixel region 280 b. It should be noted thatdisplay 270 b corresponds to display 170 of FIG. 1 and inverted pixelregion 280 b corresponds to inverted pixel region 280 a of FIG. 2A.

Illustrated in FIG. 2B, display 270 b includes decoded frame 219.Decoded frame 219 corresponds to encoded frame 217 of FIG. 2A after thedecoder decodes encoded frame 217, such as decoder 160 of FIG. 1.Inverted pixel region 280 b no longer includes the white pixels ofinverted pixel region 280 a because the decoder has inverted theinverted pixels of encoded frame 217 back to their original color. Assuch, decoded video frame 219, when presented on display to the user,has no noticeable inverted pixels from the previously embedded metadata.

Referring now to FIG. 3A, FIG. 3A presents another example of an encodedframe of a video content, according to one implementation of the presentdisclosure. Display 370 a of FIG. 3A includes inverted pixel region 380a. It should be noted that display 370 a corresponds to display 170 ofFIG. 1 and inverted pixel region 380 a corresponds to inverted pixelregion 280 a of FIG. 2A.

Illustrated in FIG. 3A, inverted pixel region at the center of circle380 a (which is further enlarged in 380 b) includes a matrix of invertedpixels which are barely visible in the encoded frame. Inverted pixelregion is located in the shadow of the door of the encoded frame, in thebottom right hand corner region of the encoded frame, so that it is notclearly visible by the user. As such, the encoded frame could bedisplayed to the user on display 370 a without the user likely noticingthe inverted pixels of the matrix.

Referring now to FIG. 3B, FIG. 3B presents another example of a decodedframe of a video content, according to one implementation of the presentdisclosure. Display 370 b of FIG. 3B includes inverted pixel region 380b. It should be noted that display 370 b corresponds to display 170 ofFIG. 1 and inverted pixel region 380 b corresponds to inverted pixelregion 280 b of FIG. 2B.

Illustrated in FIG. 3B, inverted pixel region 380 b includes the matrixof inverted pixels from the encoded frame of FIG. 3A after the decoderhas inverted the pixels back to their original color, such as decoder160 of FIG. 1. As such, the decoded frame could be displayed to the useron display 370 b without any inverted pixels from the encoded frame.

Now referring to FIG. 4, FIG. 4 shows a flowchart illustrating a methodfor embedding metadata into video contents, according to oneimplementation of the present disclosure. The approach and techniqueindicated by flowchart 400 are sufficient to describe at least oneimplementation of the present disclosure, however, other implementationsof the disclosure may utilize approaches and techniques different fromthose shown in flowchart 400. Furthermore, while flowchart 400 isdescribed with respect to FIG. 1, the disclosed concepts are notintended to be limited by specific features shown and described withrespect to FIG. 1. Furthermore, with respect to the method illustratedin FIG. 4, it is noted that certain details and features have been leftout of flowchart 400 in order not to obscure the discussion of inventivefeatures in the present application.

Referring now to flowchart 400 of FIG. 4, flowchart 400 (at 410)includes obtaining data for embedding in a video content. For example,encoder 126 may obtain metadata 118 a for embedding into video content123. In some implementations, encoder 126 may obtain all of metadata 125for embedding into video content 123, or may select only a portion ofmetadata 125.

Referring again to flowchart 400 of FIG. 4, flowchart 400 (at 420)includes determining a plurality of pixels in video content 123. Forexample, encoder 126 may determine a plurality of pixels in videocontent 123 that are to be embedded with metadata 125. Encoder 126 mayscan each frame of video content 123 to determine regions of pixelshaving substantially similar color, and embed metadata 125 into thoseregions.

Referring again to flowchart 400 of FIG. 4, flowchart 400 (at 430)includes embedding the data into the video content by inverting theplurality of pixels in the video content according to the data. Forexample, encoder 126 embeds metadata 125 into video content 123 tocreate video content with embedded metadata 128 by inverting theplurality of pixels in selected frames of video content 123 that includeregions of substantially similar color.

Now referring to FIG. 5, FIG. 5 shows a flowchart illustrating a methodfor retrieving metadata from video contents, according to oneimplementation of the present disclosure. The approach and techniqueindicated by flowchart 500 are sufficient to describe at least oneimplementation of the present disclosure, however, other implementationsof the disclosure may utilize approaches and techniques different fromthose shown in flowchart 500. Furthermore, while flowchart 500 isdescribed with respect to FIG. 1, the disclosed concepts are notintended to be limited by specific features shown and described withrespect to FIG. 1. Furthermore, with respect to the method illustratedin FIG. 5, it is noted that certain details and features have been leftout of flowchart 500 in order not to obscure the discussion of inventivefeatures in the present application.

Referring now to flowchart 500 of FIG. 5, flowchart 500 (at 510)includes determining a plurality of inverted pixels in a video content.For example, decoder 160 scans frames of video content with embeddedmetadata 128 to determine where metadata 125, including the plurality ofinverted pixels, is located within video content with embedded metadata128. In some implementations, decoder 160 may be aware of which framesand the location within the frames where metadata 125 is located basedon decoder settings 129. However, in other implementations, decoder 160may scan each frame of video content with embedded metadata 128 pixel bypixel to determine where metadata 125 is located, for example, using analgorithm that compares a pixel with its neighboring pixels.

Flowchart 500 (at 520) includes obtaining the data embedded into thevideo content according to the plurality of inverted pixels in the videocontent according to the data. For example, decoder 160 obtains metadata125 from video content with embedded metadata 128 by reading thematrices of inverted pixels embedded within video content with embeddedmetadata 128 according to metadata 125.

Next, flowchart 500 (at 530) includes outputting the data. For example,decoder 160 outputs metadata 125 on client device 150. Outputtingmetadata 125 includes utilizing metadata 125 to manage, organize, and/orcategorize video content 123 on client device 150 and/or displayingmetadata 125 on display 170.

Referring now to flowchart 500 of FIG. 5, flowchart 500 (at 540)includes inverting the plurality of inverted pixels in the video contentafter obtaining the data. For example, decoder 160 inverts the pluralityof inverted pixels within video content with embedded metadata 128 afterobtaining metadata 125 from video content with embedded metadata 128 tocreate video content 123. By inverting the plurality of inverted pixelsin video content with embedded metadata 128, the plurality of invertedpixels are inverted back to their original color.

Flowchart 500 (at 550) also includes displaying the video contentwithout or with inverting the plurality of inverted pixels. For example,client device 150 displays video content with embedded metadata 128 orvideo content 123 on display 170.

From the above description it is manifest that various techniques can beused for implementing the concepts described in the present applicationwithout departing from the scope of those concepts. Moreover, while theconcepts have been described with specific reference to certainimplementations, a person of ordinary skill in the art would recognizethat changes can be made in form and detail without departing from thescope of those concepts. As such, the described implementations are tobe considered in all respects as illustrative and not restrictive. Itshould also be understood that the present application is not limited tothe particular implementations described above, but many rearrangements,modifications, and substitutions are possible without departing from thescope of the present disclosure.

What is claimed is:
 1. A system for embedding data in a video contentincluding a movie, the system comprising: an encoder; a memory storingthe encoder and encoder setting; and a hardware processor configured toexecute the encoder according to the encoder settings to: obtain thedata; determine a plurality of pixels of an image in at least one frameof the movie; and embed the data into the image in the at least oneframe of the movie by inverting the plurality of pixels according to thedata; wherein the encoder settings are provided to a decoder for use toobtain the embedded data from the movie, and wherein the encodersettings make the decoder aware of a location of the inverted pixels ofthe image in the at least one frame of the movie.
 2. The system of claim1, wherein the plurality of pixels include pixels selected from a squaregrid of pixels.
 3. The system of claim 1, wherein prior to embedding thedata, the hardware processor is further configured to execute theencoder from the memory to: determine a number of frames of the movierequired to embed the data.
 4. The system of claim 1, wherein thedetermining the plurality of pixels includes: scanning each frame of themovie to determine at least one region of at least one frame havingpixels of consistent color, wherein the plurality of pixels are in theat least one region of the at least one frame having pixels ofconsistent color.
 5. The system of claim 1, wherein the embedded dataprovides authentication information to ensure the movie is an authenticcopy.
 6. The system of claim 1, wherein after embedding the data intothe at least one frame of the movie, the movie is transmitted across acontent delivery network.
 7. The system of claim 1, wherein the dataincludes at least one of a genre of the movie and a cast list of themovie.
 8. A method for embedding data in a video content including amovie, the method comprising: obtaining the data; determining aplurality of pixels of an image in at least one frame of the movie; andembedding the data into the image in the at least one frame of the movieby inverting the plurality of pixels according to the data; wherein theencoder settings are provided to a decoder for use to obtain theembedded data from the movie, and wherein the encoder settings make thedecoder aware of a location of the inverted pixels of the image in theat least one frame of the movie.
 9. The method of claim 8, wherein theplurality of pixels include a square matrix of pixels.
 10. The method ofclaim 8, wherein prior to embedding the data the method furthercomprises: determining a number of frames of the movie required to embedthe data.
 11. The method of claim 8, wherein the determining of theplurality of pixels includes: scanning each frame of the movie todetermine at least one region of at least one frame having pixels ofconsistent color, wherein the plurality of pixels are in the at leastone region of the at least one frame having pixels of consistent color.12. The system of claim 8, wherein the embedded data providesauthentication information to ensure the movie is an authentic copy. 13.The method of claim 8, wherein after embedding the data into the atleast one frame of the movie is transmitted across a content deliverynetwork.
 14. The method of claim 8, wherein the data includes at leastone of a genre of the movie and a cast list of the movie.
 15. A systemfor retrieving data embedded into a video content including a movie, thesystem comprising: a decoder; a memory storing the decoder; and ahardware processor configured to execute the decoder from the memory to:obtain encoder settings from the video content, wherein the encodersettings include a location of the inverted pixels of an image in atleast one frame of the movie; determine a plurality of inverted pixelsof the image from the location in the at least one frame of the movieaccording to the encoder settings; obtain the data embedded into the atleast one frame of the movie according to the plurality of invertedpixels of the image in the at least one frame of the movie according tothe data; and output the data; invert the plurality of inverted pixelsto obtain a plurality of non-inverted pixels; and display the movieincluding the plurality of non-inverted pixels.
 16. The system of claim15, wherein the hardware processor is further configured to execute thedecoder from the memory to: invert the plurality of inverted pixels inthe at least one frame of the movie after obtaining the data; anddisplay the movie after inverting the plurality of inverted pixels. 17.The system of claim 15, wherein determining the plurality of invertedpixels includes: executing an algorithm for searching one or more framesof the movie.
 18. The system of claim 15, wherein the data includes atleast one of a genre of the movie and a cast list of the movie.
 19. Thesystem of claim 15, wherein the obtaining of the data embedded into theat least one frame of the movie includes: extracting a binary code fromthe plurality of pixels; and converting the binary code into the data.20. The system of claim 15, wherein the system determines whether themovie is an authentic copy based on the embedded data.